Put last added configs at the top, instead of the bottom · Issue #2116 · 2dust/v2rayNG · GitHub

With UX design principles, in most of the GUI applications, the newer items of tables and lists are shown at the beginning, to be accessible first. For example:

And a lot more examples...

In v2rayNG: In most of the times, the user needs to click on the config which has been added a moment ago, not the oldest added config. With the current time-ascending order, the oldest added item stays at row 0 forever, and added configs are put at the end of the list so the user needs to scroll to the end each time after adding new configs to click them. When the list is too long, scrolling gets hard, so this problem becomes worse, and the user should remove old proxy configs frequently to shorten the list to overcome this problem. In other words, users need do proxy management instead of leaving this task for the app!!! Also, making the user frequently shorten the list, increases the risk of lockups because there's more chance for all configs to get expired or died at once, when the config list is not long enough.

So reverse the default initial order please!

There's also one more reason for doing this: The oldest config, in most of the cases is expired or died. Why should it stay in front of the user's eye forever? New configs should be placed at the top and older configs should get shifted to down each time the user adds a new one. So they get hidden from user's eyes when the list is long.